r? @Alexendoo

(rustbot has picked a reviewer for you, use r? to override)

This is bypassing the markdown parsing which I'm not super keen on, without fixing the root of the problem we'd still have similar issues for any other doc based lint, e.g. for missing_safety_doc

Sorry for the wait. I was in Portugal without access to a computer.
I'm going to fix this right now.

☔ The latest upstream changes (presumably #10953) made this pull request unmergeable. Please resolve the merge conflicts.

☔ The latest upstream changes (presumably #10976) made this pull request unmergeable. Please resolve the merge conflicts.

Is there something more to change in this PR?

I had the thought that it wouldn't account for spans on the other lints e.g. doc_markdown but didn't get around to testing it, if you could check that/add a test for it that'd be good

I forgot to actually add the #[warn] attribute to test it 💀

I'll add it soon

Just tested it. It does indeed bug the spans on doc_markdown. I'll prepare a fix

Fixed =)

It doesn't seem to work with

#![warn(clippy::doc_markdown)]

pub mod a {
    /**
    StructName
    */
    pub fn f() {}
}

Almost 100 days now, I'll change the approach as this isn't working.

I'll have to close this, sadly I don't have the time to research this issue further, I'll leave it free for someone else that has the time to fix it.